…deploy

The final packaging step runs Tauri's AppImage bundler, which downloads and
executes `linuxdeploy`. linuxdeploy shells out to `patchelf` (to rewrite
library rpaths) and `file` (to classify binaries). When either is missing the
Rust compile succeeds but bundling dies late with a generic
"failed to run linuxdeploy" and no obvious cause. Neither tool was installed
or checked anywhere, even though cmake/npm/etc. were.

- build_appimage.sh: add a patchelf/file preflight to the toolchain checks
  with per-distro install hints.
- install.sh: add patchelf and file to every build-dependency install line,
  and treat their absence as a missing build tool so the installer pulls them.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU

Tauri collapses any AppImage packaging failure into a bare
"failed to run linuxdeploy", hiding linuxdeploy's own diagnostics. Add a
--verbose/-v flag that passes --verbose to `tauri build` and sets VERBOSE=2 so
linuxdeploy logs at debug level, making the underlying cause (FUSE, a GTK
plugin, an unresolved library, etc.) visible.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU

The AppImage target fails at the linuxdeploy step ("failed to run linuxdeploy")
when a third-party app registers its own copy of core GLib libraries on the
system linker path via /etc/ld.so.conf.d. linuxdeploy then resolves the app's
libgio/libglib to those shadow copies and fails to bundle them because they
pull in dependencies the host lacks. The common culprit is Insync:
/usr/lib/insync/libgio-2.0.so.0 needs libselinux.so.1, absent on Arch/CachyOS,
so the GTK plugin aborts. deb/rpm don't deploy libraries, which is why only the
AppImage build breaks.

Scan /etc/ld.so.conf.d entries during the toolchain preflight and, when a
non-standard directory ships libgio-2.0/libglib-2.0, warn up front with the
exact remediation (temporarily disable the .conf, run ldconfig, build, restore)
instead of letting the build fail cryptically 20 minutes in.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU

…the build

The shadow-library problem (Insync's /usr/lib/insync breaking linuxdeploy's gtk
plugin) previously required moving the directory out of /usr/lib by hand before
every build and restoring it after — fiddly and easy to get wrong. Automate it.

With --hide-shadow-libs (needs sudo), each detected shadow directory is moved to
a sibling path outside the scanned prefix (e.g. /usr/lib/insync ->
/usr/insync.buildhide) just before `tauri build`, and an EXIT/INT/TERM trap
restores every moved directory when the build finishes or fails, so the
third-party app is never left displaced. Without the flag the behavior is
unchanged: the script only warns and now also points at the flag.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU

…ision)

On Arch/CachyOS /usr/lib64 (and often /lib) is a symlink to /usr/lib, so the
scan found the same physical directory twice — e.g. /usr/lib/insync and
/usr/lib64/insync. With --hide-shadow-libs the first was moved to
/usr/insync.buildhide and the second collided with that path, aborting the build
(the trap then restored the first). Canonicalize each candidate with readlink -f
and dedupe so each physical directory is processed once.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU

Previously the shadow-library workaround (moving Insync's /usr/lib/insync out of
linuxdeploy's search path) required the --hide-shadow-libs flag; a plain
`./build_appimage.sh` only warned and then failed at linuxdeploy. Make hiding the
default whenever a shadow directory is actually detected — it is a safe,
self-restoring operation (EXIT trap puts everything back) that only runs when
needed. Add --keep-shadow-libs / KEEP_SHADOW_LIBS=1 to opt out for anyone who
does not want the script to touch system directories. Users without such libs
are unaffected: nothing is detected, so nothing is moved and no sudo is used.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Tm6DgUP1zwuY9powkT1EHU